Fix over-localization of input values#12813
Conversation
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit d31a76a: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Pull request overview
Updates the Set-PSReadLineOption reference docs across supported PowerShell versions to prevent localization of literal input/enum values by formatting them as inline code and adding a no-loc directive.
Changes:
- Convert several parameter “valid values” lists from bold text to inline code (for example,
Audible,Windows,InlineView). - Add
no-locfront matter and updatems.datein the affected reference pages. - Apply the same doc fixes consistently across 5.1, 7.4, 7.5, and 7.6 reference sets.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 8 comments.
| File | Description |
|---|---|
| reference/7.6/PSReadLine/Set-PSReadLineOption.md | Updates metadata and formats enum/value lists as inline code to avoid localization. |
| reference/7.5/PSReadLine/Set-PSReadLineOption.md | Same localization-safety formatting changes for 7.5 docs. |
| reference/7.4/PSReadLine/Set-PSReadLineOption.md | Same localization-safety formatting changes for 7.4 docs. |
| reference/5.1/PSReadLine/Set-PSReadLineOption.md | Same localization-safety formatting changes for 5.1 docs. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <[email protected]>
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit 6e64453: ✅ Validation status: passed
For more details, please refer to the build report. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit 09ead99: ✅ Validation status: passed
For more details, please refer to the build report. |
PR Summary
Fix over-localization of input values
PR Checklist